Purpose

It's crucial to never store private keys, such as the one in private_key.pem, in a public GitHub repository or any publicly accessible location. Doing so can expose sensitive information and compromise the security of your systems.

To use this key in your project securely, consider the following best practices:

Use Environment Variables: Store the private key in an environment variable and load it in your application at runtime.
Use a Secret Manager: Utilize a secure secret management service like Azure Key Vault, AWS Secrets Manager, or HashiCorp Vault to store and retrieve the key securely.
Add to .gitignore: Ensure that private_key.pem is listed in your .gitignore file to prevent accidental commits.
Audit Your Repository: If this key has already been committed to a repository, even temporarily, consider it compromised. Revoke it immediately and generate a new one.
If you need assistance implementing any of these steps, feel free to reach out!

Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe: Improve Security